| Package | hl7.fhir.uv.cmhaffr2 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/fhir/uv/cmhaffr2/https://build.fhir.org/ig/HL7/cmhaff-ig/Requirements-CMHAFFR2-AST.1.html |
| Url | http://hl7.org/fhir/uv/cmhaffr2/Requirements/CMHAFFR2-AST.1 |
| Version | 2.0.1 |
| Status | active |
| Date | 2025-01-30T10:38:20+00:00 |
| Name | AST_1_App_and_Data_Removal |
| Title | AST.1 App and Data Removal (Header) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Generated Narrative: Requirements CMHAFFR2-AST.1
| AST.1#115 | SHALL | An app Account Holder can remove an app from a mobile device at any time. |
| AST.1#116 | SHALL | An app Account Holder is informed of the consequences of removing the app (e.g., loss of locally-stored data) from a smartphone and given an opportunity to confirm the removal of the app before the app is removed. |
| AST.1#117 | SHALL | An app Account Holder can close an associated account or data store associated with the app. |
| AST.1#118 | SHALL | An app Account Holder is informed of the consequences of deleting the account and is given an opportunity to confirm closing the account before it is closed. |
| AST.1#119 | SHALL | The user shall be informed that data that was part of the account may have been transmitted to other systems, outside of the account itself, and may persist. For example, suppose the user collects device data in an app, and transmits that data to an EHR which stores it as PGHD. In this case, the user shall be informed that deleting the account may not delete the data that is now in the EHR. |
| AST.1#120 | SHOULD | Before closing an app account, the account holder can download data generated by the account holder or a proxy subject of the account holder to a data set under the full control of the account holder (data portability). |
| AST.1#121 | SHALL | [The device permits remote or external access to device data] Any PHI or PII stored on a device can be wiped remotely by the account holder without deleting the account which is related to the wiped data. |
| AST.1#122 | SHOULD | Clear criteria are set and communicated to the user regarding the deletion of data, including automatic deletion if the user has not used the app for a specified period. |
FHIR{
"resourceType" : "Requirements",
"id" : "CMHAFFR2-AST.1",
"meta" : {
"profile" : [
"http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/FMHeader"
]
},
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: Requirements CMHAFFR2-AST.1</b></p><a name=\"CMHAFFR2-AST.1\"> </a><a name=\"hcCMHAFFR2-AST.1\"> </a><a name=\"CMHAFFR2-AST.1-en-US\"> </a><table class=\"grid\"><tr><td><b><a name=\"CMHAFFR2-AST.1-115\"> </a></b>AST.1#115</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>An app Account Holder can remove an app from a mobile device at any time.</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-AST.1-116\"> </a></b>AST.1#116</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>An app Account Holder is informed of the consequences of removing the app (e.g., loss of locally-stored data) from a smartphone and given an opportunity to confirm the removal of the app before the app is removed.</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-AST.1-117\"> </a></b>AST.1#117</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>An app Account Holder can close an associated account or data store associated with the app.</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-AST.1-118\"> </a></b>AST.1#118</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>An app Account Holder is informed of the consequences of deleting the account and is given an opportunity to confirm closing the account before it is closed.</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-AST.1-119\"> </a></b>AST.1#119</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>The user shall be informed that data that was part of the account may have been transmitted to other systems, outside of the account itself, and may persist. For example, suppose the user collects device data in an app, and transmits that data to an EHR which stores it as PGHD. In this case, the user shall be informed that deleting the account may not delete the data that is now in the EHR.</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-AST.1-120\"> </a></b>AST.1#120</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD\">SHOULD</a></td><td><div><p>Before closing an app account, the account holder can download data generated by the account holder or a proxy subject of the account holder to a data set under the full control of the account holder (data portability).</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-AST.1-121\"> </a></b>AST.1#121</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHALL\">SHALL</a></td><td><div><p>[The device permits remote or external access to device data] Any PHI or PII stored on a device can be wiped remotely by the account holder without deleting the account which is related to the wiped data.</p>\n</div></td></tr><tr><td><b><a name=\"CMHAFFR2-AST.1-122\"> </a></b>AST.1#122</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD\">SHOULD</a></td><td><div><p>Clear criteria are set and communicated to the user regarding the deletion of data, including automatic deletion if the user has not used the app for a specified period.</p>\n</div></td></tr></table></div>"
},
"url" : "http://hl7.org/fhir/uv/cmhaffr2/Requirements/CMHAFFR2-AST.1",
"version" : "2.0.1",
"name" : "AST_1_App_and_Data_Removal",
"title" : "AST.1 App and Data Removal (Header)",
"status" : "active",
"date" : "2025-01-30T10:38:20+00:00",
"publisher" : "HL7 International / Mobile Health",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/mobile"
}
]
}
],
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "CMHAFFR2-AST.1-115",
"label" : "AST.1#115",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "An app Account Holder can remove an app from a mobile device at any time."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "CMHAFFR2-AST.1-116",
"label" : "AST.1#116",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "An app Account Holder is informed of the consequences of removing the app (e.g., loss of locally-stored data) from a smartphone and given an opportunity to confirm the removal of the app before the app is removed."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "CMHAFFR2-AST.1-117",
"label" : "AST.1#117",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "An app Account Holder can close an associated account or data store associated with the app."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "CMHAFFR2-AST.1-118",
"label" : "AST.1#118",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "An app Account Holder is informed of the consequences of deleting the account and is given an opportunity to confirm closing the account before it is closed."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "CMHAFFR2-AST.1-119",
"label" : "AST.1#119",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The user shall be informed that data that was part of the account may have been transmitted to other systems, outside of the account itself, and may persist. For example, suppose the user collects device data in an app, and transmits that data to an EHR which stores it as PGHD. In this case, the user shall be informed that deleting the account may not delete the data that is now in the EHR."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "CMHAFFR2-AST.1-120",
"label" : "AST.1#120",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "Before closing an app account, the account holder can download data generated by the account holder or a proxy subject of the account holder to a data set under the full control of the account holder (data portability)."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "CMHAFFR2-AST.1-121",
"label" : "AST.1#121",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "[The device permits remote or external access to device data] Any PHI or PII stored on a device can be wiped remotely by the account holder without deleting the account which is related to the wiped data."
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/uv/cmhaffr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "CMHAFFR2-AST.1-122",
"label" : "AST.1#122",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "Clear criteria are set and communicated to the user regarding the deletion of data, including automatic deletion if the user has not used the app for a specified period."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.